Course: COMP1639 Database Engineering Contribution: 50% of course
85: Database Engineering – Term 1 – MAC PDF file required
Greenwich Course Leader: Mr Tony Valsamidis Due date:23rd November 2015
This coursework should take an average student who is up-to-date with tutorial work approximately 25 hours
Learning Outcomes:
B,C,D

Plagiarism is presenting somebody else’s work as your own. It includes: copying information directly from the Web or books without referencing the material; submitting joint coursework as an individual effort; copying another student’s coursework; stealing or buying coursework from someone else and submitting it as your own work. Suspected plagiarism will be investigated and if found to have occurred will be dealt with according to the procedures set down by the University.

All material copied or amended from any source (e.g. internet, books) must be referenced correctly according to the reference style you are using.

Your work will be submitted for electronic plagiarism checking. Any attempt to bypass our plagiarism detection systems will be treated as a severe Assessment Offence.

Coursework Submission Requirements
• An electronic copy of your work for this coursework should be fully uploaded by midnight (local time) on the Deadline Date.
• The last version you upload will be the one that is marked.
• For this coursework you must submit a single Acrobat PDF document. In general, any text in the document must not be an image (ie must not be scanned) and would normally be generated from other documents (eg MS Office using “Save As .. PDF”).
• There are limits on the file size. The current limits are displayed on the coursework submission page on the Intranet
• Make sure that any files you upload are virus-free and not protected by a password or corrupted otherwise they will be treated as null submissions.
• Comments on your work will be available from the Coursework page on the Intranet. The grade will be made available in the portal.
• You must NOT submit a paper copy of this coursework.
• All coursework must be submitted as above

The University website has details of the current Coursework Regulations, including details of penalties for late submission, procedures for Extenuating Circumstances, and penalties for Assessment Offences. See http://www2.gre.ac.uk/current-students/regs for details.
Detailed Specification
This is an individual coursework. You must design and develop a database system for a university entrance system.

Applicants may apply to five different universities. Each university may or may not interview the applicant and then may make an offer to the applicant. The offer may be conditional or unconditional. If the offer is conditional, then the conditions are stored and communicated to the student. The applicant needs to decide which of the conditional offers he or she wishes to accept, up to a maximum of three. If the condition is met when the results come out at the end of the year, the offer becomes unconditional and applicants then may accept one of the unconditional offers.

Sample required forms and reports
For universities – lists of students with their personal details, personal statements, references, grades etc.
For students – an interface that will allow them to select their choices and input their personal details.
Any other realistic reports.

The database must consist of at least six tables that have been populated with data. The database is to support queries that would typically be submitted to the system for the topical area that you have chosen. You must do the following:

• Using Chen’s or Crow’s Foot notation or any case tool to create an Entity Relationship (ER) model for your relational database. All entity types, their attributes and relationships must be clearly shown. You will also be required to show all cardinality and participation constraints. You should use some enhanced ER features in your conceptual model where it makes sense to do so.

• Map the EER model devised in part (1) into a relational data model. It must be normalised up to at least 3rd Normal Form.

• Using appropriate SQL commands create a set of database tables in an RDBMS of your choice (except Microsoft Access). You should also show all constraints used in the creation of the tables.

• Populate the database with a small amount of data. The data should be meaningful but does not need to be extensive. The following sites may be useful for quickly generating data:
o http://www.databasetestdata.com/
o http://www.generatedata.com/

• Your database must contain one view, one trigger, and an index.

• Create 10 sample queries that demonstrate the expressiveness of your database system. Your queries must demonstrate different aspects of the system.

• Your database must be accessible using the web form supplied in the course materials.

Final Report
You must submit abrief final report which must include the following:
a) A brief description of the database including any assumptions made during the design.
b) An ERD (Entity Relationship Diagram) that fully describes the database.
c) The relational schema derived from the ERD that is at least in 3NF.
d) The set of database statements used to create the tables, indexes, triggers and views used in your database. You do NOT need to include all the data and insert statements.
e) 10 queries that demonstrate the usefulness of the database. Also state why and when each query would be used. The following must be demonstrated by at least one of your queries:

o A query that uses ORDER BY
o A query that uses INNER JOINS
o A query that uses aggregate functions
o A query that uses the GROUP BY and HAVING clauses
o A query that uses a sub-query as a relation
o A query that uses a sub-query in the WHERE clause
o A query stored as a VIEW
o A query that uses a VIEW as a relation
o A query that uses partial matching in the WHERE clause
o A query that uses a self-JOIN

It is important that you provide the URL to the web interface so that we can test your database queries. Make sure that all the queries are provided in your report so that we can cut-and-paste them into the web front end for testing. At the end of your report, write a short paragraph on what you would do differently if you were to do this coursework again. The report should mostly consist of what you will be demonstrating so it should not be a major task to compile.
Demonstration
You will be required to briefly demonstrate your system in one of the laboratory sessionsprior to submission of the report.Beready to demonstrate and answer questions on your work. The system must remain on the CMS database servers until after the report is submitted.
Self-Assessment:
You will find a self-assessment sheet attached to this coursework. You are to complete this sheet and submit it with your coursework. The grade that you award yourself is NOT the final grade that you will be awarded. Your coursework will still be graded by an academic member of staff. There are 5 marks allocated for accurate self-assessment. These marks are available for accurately assessing how well you completed the coursework, so be as objective as possible when completing the form.
Self-Assessment Sheet
(Place a tick in the box that you deem to be most indicative of the quality of the work)
% No
Attempt to Very Poor Poor Fair Good Very Good Excellent
Conceptual Database Design (EER) 20
Relational schema 10
Database Implementation 20
Views and Queries 20
Report 15
Data Used 5

Self-assessment 5
Demonstration Quality 5
Total 100
Note: You must submit this self-assessment as part of the final report. The boxes in bold are for examiner use only.
General Assessment criteria:

Use the following descriptions to guide your self-assessment
Grading:

You will be graded according to the following criteria:

70-100% all requirements completed to an excellent standard

60-69% all requirements completed. However, there are a number of minor deficiencies in significant areas.

50-59% all requirements completed. However, significant improvements could be made in many areas.

40-49% all requirements completed. However, significant improvements could be made in all areas.

30-39% all requirements attempted but the overall level of understanding and performance is poor.

0-29% requirements are missing or completed to a very inadequate standard which indicates a very poor or non-existent level of understanding.

Course: COMP1639 Database Engineering Contribution: 50% of course
85: Database Engineering – Term 1 – MAC PDF file required
Greenwich Course Leader: Mr Tony Valsamidis Due date:23rd November 2015
This coursework should take an average student who is up-to-date with tutorial work approximately 25 hours
Learning Outcomes:
B,C,D

Plagiarism is presenting somebody else’s work as your own. It includes: copying information directly from the Web or books without referencing the material; submitting joint coursework as an individual effort; copying another student’s coursework; stealing or buying coursework from someone else and submitting it as your own work. Suspected plagiarism will be investigated and if found to have occurred will be dealt with according to the procedures set down by the University.

All material copied or amended from any source (e.g. internet, books) must be referenced correctly according to the reference style you are using.

Your work will be submitted for electronic plagiarism checking. Any attempt to bypass our plagiarism detection systems will be treated as a severe Assessment Offence.

Coursework Submission Requirements
• An electronic copy of your work for this coursework should be fully uploaded by midnight (local time) on the Deadline Date.
• The last version you upload will be the one that is marked.
• For this coursework you must submit a single Acrobat PDF document. In general, any text in the document must not be an image (ie must not be scanned) and would normally be generated from other documents (eg MS Office using “Save As .. PDF”).
• There are limits on the file size. The current limits are displayed on the coursework submission page on the Intranet
• Make sure that any files you upload are virus-free and not protected by a password or corrupted otherwise they will be treated as null submissions.
• Comments on your work will be available from the Coursework page on the Intranet. The grade will be made available in the portal.
• You must NOT submit a paper copy of this coursework.
• All coursework must be submitted as above

The University website has details of the current Coursework Regulations, including details of penalties for late submission, procedures for Extenuating Circumstances, and penalties for Assessment Offences. See http://www2.gre.ac.uk/current-students/regs for details.
Detailed Specification
This is an individual coursework. You must design and develop a database system for a university entrance system.

Applicants may apply to five different universities. Each university may or may not interview the applicant and then may make an offer to the applicant. The offer may be conditional or unconditional. If the offer is conditional, then the conditions are stored and communicated to the student. The applicant needs to decide which of the conditional offers he or she wishes to accept, up to a maximum of three. If the condition is met when the results come out at the end of the year, the offer becomes unconditional and applicants then may accept one of the unconditional offers.

Sample required forms and reports
For universities – lists of students with their personal details, personal statements, references, grades etc.
For students – an interface that will allow them to select their choices and input their personal details.
Any other realistic reports.

The database must consist of at least six tables that have been populated with data. The database is to support queries that would typically be submitted to the system for the topical area that you have chosen. You must do the following:

• Using Chen’s or Crow’s Foot notation or any case tool to create an Entity Relationship (ER) model for your relational database. All entity types, their attributes and relationships must be clearly shown. You will also be required to show all cardinality and participation constraints. You should use some enhanced ER features in your conceptual model where it makes sense to do so.

• Map the EER model devised in part (1) into a relational data model. It must be normalised up to at least 3rd Normal Form.

• Using appropriate SQL commands create a set of database tables in an RDBMS of your choice (except Microsoft Access). You should also show all constraints used in the creation of the tables.

• Populate the database with a small amount of data. The data should be meaningful but does not need to be extensive. The following sites may be useful for quickly generating data:
o http://www.databasetestdata.com/
o http://www.generatedata.com/

• Your database must contain one view, one trigger, and an index.

• Create 10 sample queries that demonstrate the expressiveness of your database system. Your queries must demonstrate different aspects of the system.

• Your database must be accessible using the web form supplied in the course materials.

Final Report
You must submit abrief final report which must include the following:
a) A brief description of the database including any assumptions made during the design.
b) An ERD (Entity Relationship Diagram) that fully describes the database.
c) The relational schema derived from the ERD that is at least in 3NF.
d) The set of database statements used to create the tables, indexes, triggers and views used in your database. You do NOT need to include all the data and insert statements.
e) 10 queries that demonstrate the usefulness of the database. Also state why and when each query would be used. The following must be demonstrated by at least one of your queries:

o A query that uses ORDER BY
o A query that uses INNER JOINS
o A query that uses aggregate functions
o A query that uses the GROUP BY and HAVING clauses
o A query that uses a sub-query as a relation
o A query that uses a sub-query in the WHERE clause
o A query stored as a VIEW
o A query that uses a VIEW as a relation
o A query that uses partial matching in the WHERE clause
o A query that uses a self-JOIN

It is important that you provide the URL to the web interface so that we can test your database queries. Make sure that all the queries are provided in your report so that we can cut-and-paste them into the web front end for testing. At the end of your report, write a short paragraph on what you would do differently if you were to do this coursework again. The report should mostly consist of what you will be demonstrating so it should not be a major task to compile.
Demonstration
You will be required to briefly demonstrate your system in one of the laboratory sessionsprior to submission of the report.Beready to demonstrate and answer questions on your work. The system must remain on the CMS database servers until after the report is submitted.
Self-Assessment:
You will find a self-assessment sheet attached to this coursework. You are to complete this sheet and submit it with your coursework. The grade that you award yourself is NOT the final grade that you will be awarded. Your coursework will still be graded by an academic member of staff. There are 5 marks allocated for accurate self-assessment. These marks are available for accurately assessing how well you completed the coursework, so be as objective as possible when completing the form.
Self-Assessment Sheet
(Place a tick in the box that you deem to be most indicative of the quality of the work)
% No
Attempt to Very Poor Poor Fair Good Very Good Excellent
Conceptual Database Design (EER) 20
Relational schema 10
Database Implementation 20
Views and Queries 20
Report 15
Data Used 5

Self-assessment 5
Demonstration Quality 5
Total 100
Note: You must submit this self-assessment as part of the final report. The boxes in bold are for examiner use only.
General Assessment criteria:

Use the following descriptions to guide your self-assessment
Grading:

You will be graded according to the following criteria:

70-100% all requirements completed to an excellent standard

60-69% all requirements completed. However, there are a number of minor deficiencies in significant areas.

50-59% all requirements completed. However, significant improvements could be made in many areas.

40-49% all requirements completed. However, significant improvements could be made in all areas.

30-39% all requirements attempted but the overall level of understanding and performance is poor.

0-29% requirements are missing or completed to a very inadequate standard which indicates a very poor or non-existent level of understanding.